Some of the more common questions asked about FreePPP and MacPPP:
Table of Contents:
1) What is FreePPP and how is it different than MacPPP?
2) Why is the Open button in Config PPP greyed out?
3) What does 'FreePPP: Insufficient memory to Initialize Link Access Protocol' mean?
4) How do I configure Open Transport's TCP/IP control panel to use FreePPP?
5) What is Serial DMA 2.0.2 and do I need it?
6) Why don't Config PPP or the PPP extension show up in my Extension Manager?
7) How can I configure FreePPP for use with a callback server?
8) Why doesn't setting an Echo Interval catch dropped connections?
9) What script commands are supported by FreePPP?
10) Does FreePPP support network modems?
11) Why does FreePPP/MacPPP sometimes spontaneously connect?
12) Why can't I select port speeds of 14400 or 28800 in FreePPP?
13) Is a 115K or 230K port speed really going to be faster than 57.6K?
14) What do I need to use 115K or 230K port speeds?
15) Does FreePPP make a GeoPort Telecom Adapter go faster?
16) Why does FreePPP dial when my Mac starts up?
17) Why do I get PPP Wait Timeout errors?
18) Why do I suddenly get disconnected after link establishment?
19) How do I configure FreePPP for use with TIA?
20) How do I configure FreePPP to use CHAP authentication?
21) How do I change the dial command to make my ISDN TA happy?
Answers:
1) What is FreePPP and how is it different than MacPPP?
MacPPP was developed by Larry J. Blunk and others at Merit Network, Inc. and was last revised in 1993 with the release of MacPPP 2.0.1.
FreePPP is a group effort, by the not so coincidentally named FreePPP Group, aimed at 'unifying' the various enhancments to MacPPP that have been released since 2.0.1 as well as coordinating the efforts of the people making these enhancments. The folks in the FreePPP Group that have contributed to version 1.0.5 of FreePPP are, in alphabetical order: Yan Arrouye, Steve Brecher, Jim Browne, Alec Carlson, Steve Dagley, Tom Evans, Joe Husk, Cliff McCollum, Edward Moy, Richard Reynolds and John Stephen.
Notable features in FreePPP not present in MacPPP are compatability with Open Transport and support for the CHAP authentication protocol used by some of the larger Internet service providers (such as internetMCI).
2) Why is the Open button in Config PPP greyed out?
This indicates MacTCP is not configured to use PPP as the connection method. Open the MacTCP control panel and verify that the PPP icon is hilited. If it already is, switch the selection to one of the others shown and then back to PPP. Restart your Mac. If the Open button in Config PPP is still dimmed try one of the following:
a) Zap the PRAM (Parameter RAM) of your Mac by simultaneously holding down the option-command-P-R keys while restarting. Keep holding the keys until your Mac has made the startup sound a couple of times. Now configure MacTCP to use PPP.
b) If a doesn't work restrt your Mac with the shift key held down to disable extensions. Trash the MacTCP DNR file in the System folder and the MacTCP Prep file in the Preferences folder (MacTCP will automatically re-create these files). Then reboot.
3) What does 'FreePPP: Insufficient memory to Initialize Link Access Protocol' mean?
The PPP extension does not load itself - it is loaded by MacTCP or Open Transport. When MacTCP loads the extension it's possible there will not be enough memory available in the System heap for FreePPP to allocate the memory it needs due to other extensions allocating large amounts of memory. This results in the error message 'FreePPP: Insufficient memory to Initialize Link Access Protocol' being displayed when the Finder loads and FreePPP will be disabled. There are two possible workarounds. If you have Conflict Catcher or Now Startup Manager there is an option to reserve system memory which should be set to about 96K. If you don't have Conflict Catcher or Now Utilities (we recommend both highly) try adding a space to the beginning of MacTCP control panel file name to force it to load earlier. Under Open Transport this problem should never occur as it loads FreePPP right after the MacOS logo screen is shown.
4) How do I configure Open Transport's TCP/IP control panel to use FreePPP?
OT 1.0.x Warning
As of this writing Open Transport 1.0.8 is the current version and can be ftp'd from ftp.support.apple.com. If you are using any earlier version of OT I strongly recommend updating to 1.0.8 as it is the first version that will allow Eudora to send mail reliably.
Until Open Transport 1.1 is released you must re-boot between PPP sessions if you have a dynamically assigned IP address. Dynamically means that the server assigns a different address assigned to your Mac each time you connect. Most Internet service providers (ISP) work this way. If you have a statically assigned, i.e. permanently assigned, IP address, you should be able to connect and disconnect without re-booting. If this is important to you now ask your ISP about a static address - they're usually available for an additional fee.
There is a possible workaround to re-booting - several people have reported that turning TCP/IP off and on again before re-opening a session enables them to connect succesfully. You do this in the TCP/IP Options dialog shown when you click on the Options… button in the TCP/IP control panel (User Mode must be set to Advanced).
Configuring OT 1.0.8
With Open Transport 1.0.7 or 1.0.8 the proper settings for the TCP/IP control panel to use FreePPP are:
- Connect via: MacPPP
- Configure: Manually
- Domain name: (your ISP's domain name here - i.e. company.com NOT mail.company.com)
- Name server addr.: (your ISP's name server address in dot notation - i.e. 198.1.1.1)
Note: you can enter multiple name server addresses in this field
All other fields should be left blank - especially the Subnet mask: and IP Address fields.
Configuring OT 1.1
With Open Transport 1.1 there is now a Configure: Using PPP Server option which is what you should use when connecting via FreePPP. When this configuration is selected there are only two fields available:
- Name server addr.: Your ISP's name server address in dot notation - i.e. 198.1.1.1
Note: you can enter multiple name server addresses in this field and should ask your ISP for an 'alternate' name server address to add to this field.
- Search domains: Your ISP's domain name here - i.e. company.com NOT mail.company.com.
You can also put additional domain names here to be used to find addresses for incomplete name specs (i.e. you can use just 'mail' instead of 'mail.company.com' if 'company.com' is one of your search domains).
5) What is Serial DMA 2.0.2 and do I need it?
Serial DMA 2.0.2 is a new improved version of the DMA capable serial driver for all Macs with the GeoPort serial architecture. If you have one of these machines I recommend you get this update - especially if you are using the 115K or 230K DTE rates supported by FreePPP. You can obtain Serial DMA 2.0.2 from ftp.support.apple.com with the following URL:
If you upgrade to System 7.5.3 the Serial DMA 2.0.2 extension is not needed as it is built into System 7.5.3.
Known Serial DMA 2.0.2 Problems
Serial DMA 2.0.2 is not compatible with the extension named Serial Port Arbitrator (from ARA) on PCI PowerMacs and will cause a crash at startup. Since Serial Port Arbitrator does not show up in most Extension Managers you must manually remove it (it's not necessary for ARA to work).
The Global Village extension (sorry, I don't know the name) must load after the Serial DMA 2.0.2 extension. If you are using a Global Village modem, you should add a space to the beginning of the Serial DMA 2.0.2 Extension's file name.
Serial DMA 2.0.2 should not be used with the extension 'ASFU Fixer' which was required for the GDT Softworks PowerPrint printer adapter. Versions of the PowerPrint adapter with a small hole in the adapter plug that goes into the printer (i.e. those sold in the last 6 months or so) are compatible with Serial DMA 2.0.2. If you have an older adapter contact GDT Softworks about updates.
6) Why don't Config PPP or the PPP extension show up in my Extension Manager?
The Config PPP control panel and the PPP extension do not show up in most extension manager list. Basically it's because they don't do anything by themselves. The PPP extension is loaded by MacTCP/OT so turning off MacTCP/OT effectively turns off FreePPP (it's also a file type that most extension managers don't recognize). The control panel doesn't have any code that's loaded at system startup time (i.e INIT code) so most extension managers simply ignore it. Conflict Catcher 3 can be configured to display both files if you want to be able to see/control them.
7) How can I configure FreePPP for use with a callback server?
The following is contributed by Joop J. van Vaals, Ph.D. <vaals@mswe.dnet.ms.philips.nl>
Note that the script commands to substitute name and password from the Authentication dilaog changed with FreePPP 1.0.3.
I have found the solution to a question a posted in an earlier article on how to
script FreePPP in a situation where I first have to call the internet provider,
next hang-up and then I'm called back and have to enter username and password.
Since the script part only is activated following a [connect] prompt, the hang-up
command has to be entered in the 'Phone num' box in Config PPP, directly
following the phone number. So in my situation I have to enter the following in
Config PPP (using FreePPP 1.0.2):
* Phone num box: atdt1234567890w12345612345,;S8S8S8H
* Modem Init box: at&f1w1s95=44s0=1
* Connect Script: Wait timeout = 180 secs to allow for the dial-back delay
wait Username: no CR
out \u CR
wait Password: no CR
out \p CR
wait nl-ts-0> no CR
out ppp default CR
* In the Authentication I have entered my user id and password.
In the above, S8 is the command for a 1 sec (,) delay, H is the hang-up command.
This cannot be submitted in the Connect Script, since that waits for the
[connect] prompt, and ATH has to be submitted before that is received to enable
the server to call-back and make a 'connect'.
I had tried before to include the <CR> (which is given following the tel.nr. in
the Terminal window input) by including the command S3, but that is exactly
what should not be done.
This works for me to replace the input I otherwise have to enter manually
in the Terminal window as listed below.
>When using the terminal window I give the following commmands:
>
>at&f1w1s95=44s0=1 <CR> (modem init string for GV Platinum and
> 'auto-answer after one ring')
>[ok]
>atdt1234567890w12345612345,; <CR> (to dial, wait for tone, issue a code,
> wait 2 sec, and return to command mode)
>[ok]
>ath <CR> (to hang up the line)
>[ok]
> so, at this point the telephone connection is actually broken,
> and typically in 10-100 seconds I'm called back by my internet provider
> (this is done for security reasons since via this server there is also
> direct access to confidential information, not open to the public).
> So, after the phone rings once, the modem picks up the phone (ats0=1)
>
>[ring]
>
> and after handshaking the server responds with among others
> (there is also some speed info and a broadcast message from the server):
>
>[connect] (after [connect] I do not have to press <CR>)
>
>[username:] my_username <CR>
>[password:] my_password <CR>
>[nl-ts-0>] ppp default <CR>
>[some messages and than garbage characters start to appear]
>
>
>So now the question is how to translate this into something to set up
>FreePPP so that everything works automatically.
>When I understand it correctly, the connect script is waiting for a
>[connect] string and is only activated following the [connect] string
>received. Since I do not have to give a <CR> after the connect, I supposed
>that the connect script than whould simply look like:
>
>wait Username: no CR
>out \u CR
>wait Password: no CR
>out \p CR
>wait nl-ts-0> no CR
>out ppp default CR
>
>The modem init string I entered into FreePPP is: at&f1w1s95=44s0=1
>
>The difficult is part is after dialing the telephone number and code when
>I would have to give in the terminal window a <CR>, wait for [ok]
>(which is always within 1-2 secs),
>and give ath <CR> to hang up the line so that I can be called back.
>I guess that all this has to be entered one way or another into the
>'Phone num' box if I understand things correctly.
>So I need the 'translation' (to be set in the 'Phone num' box of FreePPP)
>of the following commands given otherwise in the Terminal window
>(supposing that the connect script is waiting for and is subsequently
>activated by the [connect] response):
>
>atdt1234567890w12345612345,; <CR> (to dial, wait for tone, issue a code,
> wait 2 sec, and return to command mode)
>[ok]
>ath <CR> (to hang up the line)
>
>I guess that the \d command is only valid within the connect script, since
>my Global Village Platinum modem can't handle that command. I've tried
>things like:
>atdt1234567890w12345612345,;ats3s8aths3 (where s3 is the carriage return
>and s8 is the definition of the time delay of the comma in the dial
8) Why doesn't setting an Echo Interval catch dropped connections?
Try adding E0 (that's a zero as the second character) to your modem init string. When the line drops the modem returns to command mode which usually echoes any chacters it receives. When this happens to an echo request packet FreePPP sees the echoed chacters as a request to it for an echo response which it generates and then gets echoed back fulfilling the echo request (can we say circular reference?). Adding the E0 will prevent this loop from occuring. Thanks to ??? (sorry, lost the original posting) for explaining this on comp.sys.mac.comm recently.
9) What script commands are supported by FreePPP?
The backslash (\) is a reserved character in the FreePPP/MacPPP Connect Script dialog box.
The original MacPPP script commands are:
Commands useable in both Out and Wait strings:
\r carriage return
\^ literal '^'
\\ literal '\'
\nnn 8-bit octal value
The following can be used only in Out strings:
\b send a break (100 milliseconds)
\d delay for one second
\t invoke the MacPPP terminal emulator
FreePPP 1.0.3 and later extend the scripting commands for Out strings with:
\a"prompt" ask for echoed text, "prompt" defaults to "Username:"
\A"prompt" ask for echoed text, "prompt" defaults to "Username:"
\p"prompt" ask for bulleted text, "prompt" defaults to "Password:"
\P"prompt" ask for bulleted text, "prompt" defaults to "Password:"
Notes:
• Lowercase '\a' and '\p' prompt during a connection when they are run across with
the connect script.
• Uppercase '\A' and '\P' prompt prior to a connection and/or are preloaded from
the authentication area.
• Only the text entered will be sent. It is up to you to add delays and returns as
needed.
Limitations:
• Only one '\a' and '\p' per line.
- If more than one of each is found per line then only the first of each requested
will be used to prompt.
- However, the data will be sent each time '\a' or '\p' is run accross.
• Only one '\A' and '\P' per connect script.
- If more than one of each is found per line then only the first of each requested
will be used to prompt.
- However, the data will be sent each time '\A' or '\P' is run accross.
Examples:
• \AWhat's your Username:\r\d\PGimme your Password:\r\d
• \aUser ID:\r
\p\r
• \ASecureID:\r
\pSecureID Password:\aSecureID Number:\r
10) Does FreePPP support network modems?
I have tested FreePPP with Stalker's PortShare Pro v2.6 and it works fine when the Force Auto-Status option is turned on. Other network modem solutions may or may not work. If FreePPP gets an error trying to establish a connection using a networked modem and a connect script try using Terminal Window mode and manually establishing the connection.
11) Why does FreePPP/MacPPP sometimes spontaneously connect?
This should only happen when using MacTCP (thanks to Vladimir Butenko of Stalker Software for finding the cause). There is an internal timer in MacTCP that will cause a connection attempt approximately 5.5 hours after a session is closed. FreePPP adds the Disable Auto Connect option which eliminates this problem by requiring all sessions to be manually opened.
12) Why can't I select port speeds of 14400 or 28800 in FreePPP?
These port speeds should not be used. Modem speeds are expressed two different ways. There's the modem to computer speed (DTE rate) and the raw modem to modem speed (DCE rate). Modems with data compression features compress the data before they send it so your effective throughput is generally greater than the DCE rate but can never be higher than the DTE rate. This is why you want to set the DTE rate higher than the DCE rate. In addition, some modems don't work with DTE rates of 14400 or 28800 so they were removed from FreePPP.
13) Is a 115K or 230K port speed really going to be faster than 57.6K?
It depends on the data being transferred and the type of connection you have.
For modems, the V.42bis data compression standard is theoretically capable of 4:1 compression. Therefore you'd want a 115Kbps DTE rate to fill a 28.8Kbps V.34 link w/V.42bis compression. In the real world most data doesn't usually compress better than 2:1 so a DTE rate of 57.6K is usually sufficient. On the other hand I've seen better than 8000 bytes/sec using Fetch to ftp a highly compressible text file (400K of repeating 'abcdef') over a 24K V.34 link. Using the Electronic Frontier Foundation's "Big Dummy's Guide to the Internet" as a test file I've gotten in the neighborhood of 6200 bytes/sec. Keep in mind that the port speed has no bearing on the connect rate of your modem. A 28.8K connection requires very clear phone lines at each end. Connect rates of 26.4K or 24K are much more common.
The only modem I know of that supports a DTE rate of 230Kbps is the Hayes Optima 288. They use a modified version of the V.42bis compression routine that's theoretically capable of 8:1 compression (as opposed to normal V.42bis' 4:1 max). Unfortunately I don't have one so I can't say what sort of throughput my test files would have at the 230K DTE rate.
With a serial ISDN Terminal Adapter (sometimes called an ISDN modem in marketingspeak) you get a 64Kbps link with one B channel or a 128Kbps link with two B channels. Compression would make throughput even faster. What port speed you should use is dependent on the ISDN equipment you are using. As of this writing the Motorola BitSURFR and BitSURFR Pro as well as the 3Com Impact Terminal Adapters max out at a 115K DTE rate
14) What do I need to use 115K or 230K Port Speeds?
You need a Mac with the GeoPort DMA serial architecture and a 28.8 modem or ISDN Terminal Adapter attached to the built-in Modem or Printer port. The increased interrupt load for the higher rates is too much for non-serial DMA Macs so I'd strongly recommend against using it on one although I don't currently check the Mac type (and as near as I can tell it's impossible to check to see if the serial ports are of the GeoPort variety). If you insist on trying it on a IIfx or Quadra 900/950 you must make sure that you have set the serial ports to 'compatible' mode using the Serial Switch Control Panel. If you don't, you'll crash your Mac when you try to connect. Since I already said you shouldn't be using this software on one of these machines I don't consider this a bug so consider yourself warned.
If an add on serial port board supports the new serial driver calls, introduced with Serial DMA 2.0.2, to select 115K and 230K DTE rates FreePPP should automatically work with it.
Of course if your dialup PPP provider isn't using 28.8 modems or ISDN service with a 115K or 230K DTE rate on their end you won't see any difference. That part I can't help you with. :-)
Note - If your modem or ISDN TA doesn't list support for a 115K or 230K DTE rate in their documentation, don't try to use it. One of the most common problem reports I get is folks trying to use the faster rates on equipment that doesn't support it.
15) Does FreePPP make a GeoPort Telecom Adapter go faster?
No, it does work with a GeoPort Telecom Adapter (TCA) however. Why doesn't it make the TCA go faster? Because the TCA pod isn't really a modem. It's just the hardware required to connect your Mac to the phone lines or POTS (Plain Old Telephone Service). The rest of the modem functions are implemented inside your Mac. Apple may implement a V.34 version of the Express Modem software but I wouldn't hold my breath waiting for it. I wouldn't recommend it on the PowerMac either as the current V.32bis implementation of the software seems to be good for approximately a 30% slowdown on a 6100/60AV. Eventually Apple is supposed to release a GeoPort ISDN Adapter but I have no idea when or if the current version of FreePPP will support it.
16) Why does FreePPP dial when my Mac starts up?
Important - As of FreePPP 1.0.4 connections at startup time are not supported and may cause a crash.
FreePPP tries to open a connection whenever it sees TCP/IP packets unless the Disable Auto Connect is turned on (Or the Hard Close command was used to terminate a MacPPP session but this isn't remembered on restart). There are several extensions that send TCP/IP packets when they load at boot time so this is why you get connection attempts during startup. The extensions (or the programs that install them) that I know of that do this are: Apple's SNMP agent software installed as part of the full MacTCP install, Farallon's Timbuktu Pro, ON Technology's Meeting Maker XP, a shareware control panel called Network Time (I'm not sure of this name as I haven't actually seen this one), and one of the extensions that is used to support the Cayman GatorBox AppleTalk to TCP/IP router (sorry, lost the message with the exact info). See if there's a configuration option to turn off this functionality at startup or remove the offending extension (anyone ever use the SNMP software?).
Another extension that will cause connection attempts every time an application quits is ZapTCP. Since this extension is intended solely as a debugging aid for folks writing apps using TCP/IP packets I highly recommend removing it unless you know you need it.
17) Why do I get PPP Wait Timeout errors?
Here are two common causes of the 'PPP Wait Timeout - Waiting on: OK' error:
1) An incompatible Port Speed is selected. This may be a rate higher than supported by your modem or a speed that you'd think was supported but isn't. Port speeds of 14400 and 28800 are examples of the latter and are discussed above. For Mac/Modem configurations that don't support the 115K or 230K port speeds, stick with the 38400 or 57600 rates as these should be supported by every 14.4 and 28.8 modem on the market today.
2) You have fax software installed that is conflicting with FreePPP/MacPPP. Try turning off the answer incoming faxes feature if it's turned on in your fax software. If that doesn't do the trick try turning off the fax software completely with an extension manager.
18) Why do I suddenly get disconnected after link establishment?
If you don't have a 'hardware handshake' cable and you have hardware flow control enabled (see the section on Flow Control in the accompanying 'Installing MacPPP' document for details) you will usually get a disconnect soon after a PPP session is established. Most modems these days come with a bundled hardware handshake cable. It's when a new modem is connected with the cable that was used for an old 2400 bps modem that causes a problem. In short, if the modem came with a cable be sure to use it. If the modem didn't come with a cable, make sure the one you're using supports hardware handshake. For the technically inclined this means a cable with pins 4 & 20 on the 25-pin connector for the modem are connected to pin 1 on the 8-pin connector for the Mac.
Another reason for the Link Dead problem is that some badly configured PPP servers send clear text before starting PPP. You can see this by using the Terminal Window to login manually and looking for text after you send your password (you should see what look like garbage characters if PPP is starting up). The solution to this problem is to add delays to your connect script after you send the password - two or three \d entries along with the <CR> box checked on the next line down should suffice.
19) How do I configure FreePPP for use with TIA?
Send email to tia-mac-ppp@marketplace.com to get instructions on how to configure FreePPP and TIA.
20) How do I configure FreePPP to use CHAP authentication?
FreePPP will automatically detect a CHAP request from a PPP server. Just enter your login name and password in the Authentication dialog for your server configuration.
21) How do I change the dial command to make my ISDN TA happy?
Warning - not for the faint of heart.
Versions of FreePPP prior to 1.0.5 had hard coded 'ATDT' for tone dialing and 'ATDP' for pulse dialing. With FreePPP 1.0.5 and later these commands are loaded from the ID#130 'STR#' resource (the 2nd and 3rd strings respectively) in the PPP extension. You can edit these strings with a tool like ResEdit.
